NTISthis.com

Evidence Guide: ICTSAS514 - Perform integration tests

Student: __________________________________________________

Signature: _________________________________________________

Tips for gathering evidence to demonstrate your skills

The important thing to remember when gathering evidence is that the more evidence the better - that is, the more evidence you gather to demonstrate your skills, the more confident an assessor can be that you have learned the skills not just at one point in time, but are continuing to apply and develop those skills (as opposed to just learning for the test!). Furthermore, one piece of evidence that you collect will not usualy demonstrate all the required criteria for a unit of competency, whereas multiple overlapping pieces of evidence will usually do the trick!

From the Wiki University

 

ICTSAS514 - Perform integration tests

What evidence can you provide to prove your understanding of each of the following citeria?

Prepare for test

  1. Prepare test environment
  2. Prepare test scripts (online test) or test run (batch test) for running
  3. Review expected results against test and acceptance criteria
  4. Confirm pre-existing modules and compile modification logs
  5. Perform static tests of each point of integration and verify correctness of arguments, positional parameters and return values in each integration suite
  6. Review results of earlier component testing and ensure critical issues are identified and considered
Prepare test environment

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Prepare test scripts (online test) or test run (batch test) for running

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Review expected results against test and acceptance criteria

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Confirm pre-existing modules and compile modification logs

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Perform static tests of each point of integration and verify correctness of arguments, positional parameters and return values in each integration suite

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Review results of earlier component testing and ensure critical issues are identified and considered

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Conduct test

  1. Select appropriate test tools
  2. Run test scripts and document results against software life cycle model
  3. Ensure that memory leakage, global name-space pollution and static variables are specifically addressed for each integration unit in line with test and acceptance criteria
  4. Follow and adopt integration standards where appropriate in line with quality benchmarks
  5. Compare test results to requirements on completion of each integration component
Select appropriate test tools

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Run test scripts and document results against software life cycle model

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Ensure that memory leakage, global name-space pollution and static variables are specifically addressed for each integration unit in line with test and acceptance criteria

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Follow and adopt integration standards where appropriate in line with quality benchmarks

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Compare test results to requirements on completion of each integration component

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Analyse and classify results

  1. Summarise and classify test results and highlight areas of concern
  2. Compare test results against requirements and design specification, and prepare report
  3. Notify operations of completion of testing where appropriate
  4. 3.4 Ensure attendees' details and comments are logged and signatures gained
  5. Schedule and conduct a feedback meeting to discuss report and possible next actions with stakeholders if necessary
  6. Ensure test reporting complies with documentation and reporting standards
Summarise and classify test results and highlight areas of concern

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Compare test results against requirements and design specification, and prepare report

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Notify operations of completion of testing where appropriate

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

3.4 Ensure attendees' details and comments are logged and signatures gained

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Schedule and conduct a feedback meeting to discuss report and possible next actions with stakeholders if necessary

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Ensure test reporting complies with documentation and reporting standards

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Assessed

Teacher: ___________________________________ Date: _________

Signature: ________________________________________________

Comments:

 

 

 

 

 

 

 

 

Instructions to Assessors

Evidence Guide

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Prepare for test

1.1 Prepare test environment

1.2 Prepare test scripts (online test) or test run (batch test) for running

1.3 Review expected results against test and acceptance criteria

1.4 Confirm pre-existing modules and compile modification logs

1.5 Perform static tests of each point of integration and verify correctness of arguments, positional parameters and return values in each integration suite

1.6 Review results of earlier component testing and ensure critical issues are identified and considered

2. Conduct test

2.1 Select appropriate test tools

2.2 Run test scripts and document results against software life cycle model

2.3 Ensure that memory leakage, global name-space pollution and static variables are specifically addressed for each integration unit in line with test and acceptance criteria

2.4 Follow and adopt integration standards where appropriate in line with quality benchmarks

2.5 Compare test results to requirements on completion of each integration component

3. Analyse and classify results

3.1 Summarise and classify test results and highlight areas of concern

3.2 Compare test results against requirements and design specification, and prepare report

3.3 Notify operations of completion of testing where appropriate

3.4 Ensure attendees' details and comments are logged and signatures gained

3.5 Schedule and conduct a feedback meeting to discuss report and possible next actions with stakeholders if necessary

3.6 Ensure test reporting complies with documentation and reporting standards

Required Skills and Knowledge

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Prepare for test

1.1 Prepare test environment

1.2 Prepare test scripts (online test) or test run (batch test) for running

1.3 Review expected results against test and acceptance criteria

1.4 Confirm pre-existing modules and compile modification logs

1.5 Perform static tests of each point of integration and verify correctness of arguments, positional parameters and return values in each integration suite

1.6 Review results of earlier component testing and ensure critical issues are identified and considered

2. Conduct test

2.1 Select appropriate test tools

2.2 Run test scripts and document results against software life cycle model

2.3 Ensure that memory leakage, global name-space pollution and static variables are specifically addressed for each integration unit in line with test and acceptance criteria

2.4 Follow and adopt integration standards where appropriate in line with quality benchmarks

2.5 Compare test results to requirements on completion of each integration component

3. Analyse and classify results

3.1 Summarise and classify test results and highlight areas of concern

3.2 Compare test results against requirements and design specification, and prepare report

3.3 Notify operations of completion of testing where appropriate

3.4 Ensure attendees' details and comments are logged and signatures gained

3.5 Schedule and conduct a feedback meeting to discuss report and possible next actions with stakeholders if necessary

3.6 Ensure test reporting complies with documentation and reporting standards

Evidence of the ability to:

prepare the test environment

conduct tests using appropriate test tools and integration standards and quality benchmarks

perform integration requirements for the units

determine whether the units operate according to specifications

analyse and classify results

prepare reports that comply with documentation and reporting standards.

Note: Evidence must be provided on at least TWO systems or occasions.

To complete the unit requirements safely and effectively, the individual must:

describe the key features of at least two programming languages, with detailed knowledge of programming languages required by current system/project

compare and contrast automated test tools, with detailed knowledge of features and processes of tools used for current system/project

identify input and output requirements

discuss organisational practice, standards and benchmarks relating to integration testing

analyse and describe the system or application being tested

describe key features and processes of testing techniques and tools

analyse underlying test data.